Managing vplmn configuration updates in the ue due to home plmn configuration changes

ABSTRACT

Methods and apparatus, including computer program products, are provided for managing configuration updates. In some example embodiment, there may be provided an apparatus including at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least: receive an indication regarding whether a home network of said apparatus makes a change to first configuration information stored at said home network and associated with the apparatus; and delete, in an instance in which the received indication represents the change, second configuration information stored at said apparatus, said second configuration information comprising information regarding one or more configurations associated with a visited network currently serving said apparatus and information regarding one or more configurations associated with one or more other visited networks.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/214,010, filed Mar. 26, 2021 and entitled “Managing VPLMNConfiguration Updates in the UE Due to Home PLMN Configuration Changes,”which is a continuation of U.S. patent application Ser. No. 16/417,708,filed May 21, 2019 and entitled “Managing VPLMN Configuration Updates inthe UE Due to Home PLMN Configuration Changes,” which claims the benefitof, and priority to, U.S. Provisional Application No. 62/674,465,entitled “Managing VPLMN Configuration Updates in the UE Due to HomePLMN Configuration Changes,” and filed May 21, 2018, the entire contentsof each of which are hereby incorporated herein by reference for allpurposes.

FIELD

The subject matter described herein relates to wireless technologies.

BACKGROUND

As the cellular system including the Fifth Generation (5G) systemsupports an increasing number of devices and services includingapplications with a wide range of use cases and diverse needs withrespect to bandwidth, latency, and reliability requirements, thecellular system may need to prioritize resources across the wirelessaccess network and the core network (and/or for example, prioritizingacross the control plane and the user plane) to support differentiationamong different services.

SUMMARY

Methods and apparatus, including computer program products, are providedfor managing configuration updates.

In some example embodiment, there may be provided an apparatus includingat least one processor and at least one memory including computerprogram code, the at least one memory and the computer program codeconfigured to, with the at least one processor, cause the apparatus toat least: receive an indication regarding whether a home network makes achange to a previous configuration information for the apparatus; anddelete, when the received indication represents the change, the previousconfiguration information stored at the apparatus.

In some variations, one or more of the features disclosed hereinincluding the following features can optionally be included in anyfeasible combination. The apparatus may be further caused to at least:receive configuration information including the indication. The deletionof the previous configuration information includes deletion of theprevious configuration information associated with the home network anda visiting network. The deletion of the previous configurationinformation may include at least one network slice identifier. Thedeletion may enable the apparatus to obtain updated configurationinformation for at least the visiting network currently serving theapparatus and/or the home network. The apparatus may be further causedto at least: receive the updated configuration information for at leastone other visiting network to replace the deleted, previousconfiguration information, when the indication represents the changeassociated with the home network is received. The apparatus may befurther configured to at least: wait to perform, after obtaining thereceived configuration information, a registration to obtain the updatedconfiguration information until an updated user equipment route andaccess selection policy is received. The apparatus may be further causedto at least: update configuration information for the visiting network,when the indication is received representing the change associated withthe home network; and update configuration information for the visitingnetwork only, when no indication is received that represents the changeassociated with the home network. The indication may represent the homenetwork indicating to the visiting network currently serving the userequipment that the change in the home network is to be taken intoaccount in the visiting network for configuring the apparatus.

According to some embodiments, an apparatus can be provided thatcomprises: at least one processor; and at least one memory storingcomputer program code, the at least one memory and the computer programcode being configured to, with the at least one processor, cause theapparatus to at least: receive an indication regarding whether a homenetwork of said apparatus makes a change to first configurationinformation stored at said home network and associated with theapparatus; and delete, in an instance in which the received indicationrepresents the change, second configuration information stored at saidapparatus, said second configuration information comprising informationregarding one or more configurations associated with a visited networkcurrently serving said apparatus and information regarding one or moreconfigurations associated with one or more other visited networks. Insome embodiments, the first configuration information and the secondconfiguration information are related to subscription informationassociated with said apparatus. In some embodiments, first configurationinformation and second configuration information are related to one ormore of: a quantity of network slices, a Quality of Service (QoS) typeof said network slices, or an identity of said network slices. In someembodiments, the first configuration information is different from thesecond configuration information. In some embodiments, the apparatus isfurther caused to at least: receive configured information or updatedconfiguration information including or together with the indication. Insome embodiments, the deletion of the second configuration informationincludes deletion of configuration information associated with the homenetwork of the apparatus. In some embodiments, at least one of the firstconfiguration information or the second configuration informationcomprises network slice configuration information, said network sliceconfiguration information comprising at least one network sliceidentifier. In some embodiments, the deletion enables the apparatus toobtain updated configuration information for at least one of: thevisited network currently serving the apparatus, the one or more othervisited networks, or the home network of the apparatus. In someembodiments, the apparatus is further caused to at least: receiveupdated configuration information for the visited network currentlyserving the apparatus to replace the deleted second configurationinformation, in an instance in which the indication represents thechange associated with the home network is received. In someembodiments, the apparatus is further configured to at least: wait toperform, after receiving the updated configuration information, aregistration to obtain the updated configuration information until anupdated user equipment route and access selection policy is received. Insome embodiments, the apparatus is further caused to at least: updateconfiguration information for the visited network currently serving theapparatus. In some embodiments, the indication represents the homenetwork indicating to the visited network currently serving theapparatus that the change in the home network is to be taken intoaccount in the visited network currently serving the apparatus forconfiguring the apparatus.

According to another embodiment, a method can be carried out thatcomprises: receiving, at user equipment, from a home network of the userequipment, an indication regarding whether a change has been made tofirst configuration information stored at said home network andassociated with the user equipment; and deleting, in an instance inwhich the received indication represents the change was made, secondconfiguration information stored at the user equipment, said secondconfiguration information comprising information regarding one or moreconfigurations associated with a visited network currently serving saiduser equipment and information regarding one or more configurationsassociated with one or more other visited networks. In some embodiments,the first configuration information and the second configurationinformation are related to subscription information associated with theuser equipment. In some embodiments, the first configuration informationand the second configuration information related to one or more of: aquantity of network slices, a Quality of Service (QoS) type of saidnetwork slices, or an identity of said network slices. In someembodiments, the first configuration information is different from thesecond configuration information. In some embodiments, the method canfurther comprise: receiving configuration information or updatedconfiguration information including or together with the indication. Insome embodiments, the deletion of the second configuration informationincludes deletion of configuration information associated with the homenetwork of the user equipment. In some embodiments, at least one of thefirst configuration information or the second configuration informationcomprises network slice configuration information, said network sliceconfiguration information comprising at least one network sliceidentifier. In some embodiments, the deletion enables the user equipmentto obtain updated configuration information for at least one of: thevisited network currently serving the user equipment, the one or moreother visited networks, or the home network of the user equipment. Insome embodiments, the method can further comprise: receiving updatedconfiguration information for the visited network currently serving theuser equipment to replace the deleted second configuration information,in an instance in which the indication represents the change associatedwith the home network is received. In some embodiments, the method canfurther comprise: waiting to perform, after receiving the updatedconfiguration information, a registration to obtain the updatedconfiguration information until an updated user equipment route andaccess selection policy is received. In some embodiments, the method canfurther comprise: updating configuration information for the visitednetwork currently serving the user equipment.

According to still another embodiment, a non-transitory computerreadable medium can be provided that includes program code which, whenexecuted, causes operations comprising: receiving, at user equipment,from a home network of the user equipment, an indication regardingwhether a change has been made to first configuration information storedat said home network and associated with the user equipment; anddeleting, in an instance in which the received indication represents thechange was made, second configuration information stored at the userequipment, said second configuration information comprising informationregarding one or more configurations associated with a visited networkcurrently serving said user equipment and information regarding one ormore configurations associated with one or more other visited networks.

The above-noted aspects and features may be implemented in systems,apparatus, methods, and/or articles depending on the desiredconfiguration. The details of one or more variations of the subjectmatter described herein are set forth in the accompanying drawings andthe description below. Features and advantages of the subject matterdescribed herein will be apparent from the description and drawings, andfrom the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings,

FIG. 1 depicts an example of a portion of a 5G wireless network, inaccordance with some example embodiments;

FIG. 2 depicts an example of a process flow for VPLMN configurationupdating, in accordance with some example embodiments;

FIG. 3 depicts another example of a process flow for VPLMN configurationupdating, in accordance with some example embodiments;

FIG. 4 depicts an example of a network node, in accordance with someexample embodiments; and

FIG. 5 depicts an example of an apparatus, in accordance with someexample embodiments.

Like labels are used to refer to same or similar items in the drawings.

DETAILED DESCRIPTION

In the 5G system, a user equipment (UE) may be roaming from a homepublic land mobile network (HPLMN) to a visiting public land mobilenetwork (VPLMN). When this is the case, the UE may have configurationinformation for use in the VPLMN to, for example, enable access to oneor more services that are available at the VPLMN. The configurationinformation for a UE may change due to local decisions at a VPLMN, forexample. Alternatively or additionally, the UE's configurationinformation may change due to, for example, changes in the UE'ssubscription information at the HPLMN.

To illustrate further, the UE may access a service at an HPLMN and/or aVPLMN based on the UE's configuration information, which may be based onsubscription information that indicates the allowed and/or the availableservices. The UE's subscription information may change due to, forexample, the HPLMN making or initiating changes to the UE'ssubscription, in which case the VPLMN-related configuration informationfor the one or more services may also need to be updated as well to makeit consistent with the change(s) at the HPLMN. Thus, a change in thesubscription information (which may be stored in a Unified DataManagement (UDM) node in the HPLMN) may trigger changes to the UE'sconfiguration information for operating in an HPLMN and/or a VPLMN.

The VPLMN and HPLMN configuration information may have values that aredifferent, and a mapping may be established by the VPLMN, without theHPLMN being aware of the values used locally within the VPLMN. Forexample, if the HPLMN changes a UE's subscription, the VPLMNs may needto independently update the configuration information includingsubscription related information, so the UE has up to date VPLMNinformation. To illustrate further, the subscription information at theHPLMN may change QoS or another aspect of a network slice, or it maychange entirely the fact a certain slice could be accessible, or thesubscription may include new slices the UE can use. This change maytrigger a corresponding change in the configuration information for useof the VPLMN.

When the HPLMN configuration changes with respect to the UE'ssubscription changes for example, the VPLMN configuration with respectto the UE's subscription may need an update. While the UE is registeredin a VPLMN, the HPLMN may push to the VPLMN the configurationinformation to update (which as noted stored at a network node, such asa Unified Data Manager (UDM, which may serve as a repository for storingthis and other configuration and/or subscription information). However,when the UE is visiting another VPLMN, the new VPLMN may receive the upto date configuration or subscription information for a UE but the VPLMNmay not be able to detect whether the information represents a change,as the VPLMN may not have state information for the UE's configurationor subscription information, so the UE may not be trigger the change orupdate.

In some example embodiments, when the UE receives a configurationinformation update including information related to the UE'ssubscription (e.g., network slice identifiers such as Network SliceSelection Assistance Information, NSSAI), the UE may also receive anindication, such as a cause code for the update. If the update is due toa local change in the VPLMN, the UE may update the VPLMN relatedinformation, which the UE keeps stored at the UE.

If however the indicator, such as the cause code, represents the updateis due to a change in the HPLMN configuration, such as the UE'ssubscription, the UE may store the received update as a change to theVPLMN configuration and as a change to the HPLMN configuration. For some(if not all) other VPLMNs configurations, the UE may record or indicatethat these may be invalid due to changes in HPLMN configuration.

Moreover, when the indicator, such as the cause code, represents theupdate is due to a change in the HPLMN configuration, as the UE visitsother VPLMNs the UE may operate as if the UE needs initial configurationinformation from the VPLMN (e.g., initial configuration information asif the UE visited the VPLMN for the first time). For example, the UE maydelete (e.g., remove, reset, and/or the like) all UE configurationinformation for the VPLMN(s). For the case of network slicing VPLMNconfiguration, the UE for example may remove the configured NSSAI forthe PLMN its mapping to the S-NSSAIs in the configured NSSAI for theHPLMN, the allowed NSSAI and its mapping to the S-NSSAIs in theconfigured NSSAI for the HPLMN, any rejected S-NSSAIs in the PLMN. Thisdeletion may cause the UE to appear to the network as a UE that needsinitial configuration when performing a registration procedure, and thenetwork to provide an initial configuration to the UE, when the UEaccesses as part of registration the VPLMN.

To illustrate further, when the indicator, such as the cause code,represents the update is due to a change in the HPLMN configuration, theUE may, as noted, locally delete certain configuration information, suchas a network slicing configuration information (e.g., NSSAIs as notedabove), for some, if not all, other VPLMNs. As such, when the UEperforms a registration procedure in these other VPLMNs, the UE may notsend a request for NSSAI(s), but instead may receive from the network aconfiguration for the VPLMN. This received configuration information mayinclude slice identifiers, such as a S-NSSAI, for use at a VPLMN andmapping to HPLMN values.

In some example embodiments, the UE may wait in the serving VPLMN for anupdated policy, such Vas an URSP (UE Route and access Selection policy)from the network before the UE performs a new registration procedure asthe URSP may also change, when the UE subscription to the S-NSSAIs haschanged.

FIG. 1 depicts an example of a portion of a 5G wireless network 100, inaccordance with some example embodiments.

The 5G wireless network 100 may include a user equipment (UE) 150configured to wirelessly couple to a radio access network (RAN) 152being served by a wireless access point, such as a base station,wireless local area network access point, home base station, and/orother type of wireless access point.

The network 100 may include a core network, which may include an accessand mobility management function (AMF) 154, a visiting sessionmanagement function (V-SMF) 156, a visiting policy control function(v-PCF) 160, a visiting network slice selection function (v-NSSF) 164,and/or a visiting user plane function (V-UPF) 158. In the example ofFIG. 1 , devices 152-164 may be associated with a visiting public landmobile network (VPLMN) 166.

The network 100 and/or the core network may include devices havingfunctions supporting a home public land mobile network (HPLMN) 170 aswell. For example, these devices in the HPLMN 170 may include devicesand corresponding functions for “home” wireless local area network(WLAN) access, offloading, and/or non-3GPP access. These devices mayinclude a home SMF 172, a home PCF 174, a home NSSF 176, unified datamanagement 178, an authentication server function (AUSF) 180, anapplication function (AF) 182, a home user plane function (H-UPF) 184,and a data network (DN) 186.

FIG. 1 also depicts service interfaces, such as N1, N2, N3, N4, N6, N7,N11, N15, N18, N24, and/or the like. The architecture, nodes (includingAMF, V-PCF, H-PCF, H-SMF, and V-SMF as well as other devices depicted atFIG. 1 ), and the service interfaces may be defined in accordance with astandard, such as 3GPP TS 23.501, although other standards as well asproprietary interfaces may be used.

A network slice refers to a logical network that provides specificnetwork capabilities and network characteristics. The network slice maybe considered a logical end-to-end network that can be dynamicallycreated, so that a given UE may access different network slices over thesame radio access network (e.g., over the same radio interface). Thenetwork slices can provide different services and/or have different QoSneeds/requirements. 3GPP TS 23.501, System Architecture for the 5GSystem, describes examples of network slices.

The UE's subscription information may dictate the configurationinformation related to the quantity, QoS type, and/or identity of thenetwork slices. The UE's configuration information (provided by thenetwork when registering in a PLMN, such as a VPLMN and/or HPLMN) mayinclude one or more network slice identifiers, such as one or moresingle NSSAIs (S-NSSAI). The S-NSSAI may be comprised of: a) aslice/service type (SST), which refers to the expected network slicebehavior in terms of features and services; and/or b) a slicedifferentiator (SD), which is optional information that complements theSlice/Service type(s) to differentiate amongst multiple network slicesof the same Slice/Service type.

FIG. 2 depicts an example of a process 200, in accordance with someexample embodiments. The description of FIG. 2 refers to FIG. 1 as well.

At 205, a user equipment 150 may receive, from the network,configuration information and/or an indication regarding whether theconfiguration information represents a change, such as an update or amodification, that is local to a VPLMN (which is currently serving theUE 150) or a change associated with the HPLMN, in accordance with someexample embodiments. In some example embodiments, the configurationinformation may be received in a message, such as a registration acceptor in a UE configuration update message. The indication may be includedin the configuration information or signaled separately to the UE 150.The presence of the indication may signal that the UE's HPLMN has made aconfiguration change that needs to be applied to the UE's configurationat the VPLMNs. In some implementations, the indication (or its absence)may indicate that a UE's configuration information should be updatedlocally so as to only affect the UE's configuration with the currentlyserving VPLMN, rather than other VPLMNs (or the HPLMN). In some exampleembodiments, the indication is included in the configurationinformation. For example, the configuration information may representconfiguration information for the currently serving VPLMN, and includethe indication to signal the UE 150 whether the change is needed to theUE's configuration information. Alternatively or additionally, theindication may be provided to the UE 150 separate from the configurationinformation.

When the indication represents an HPLMN configuration change (which may,for example, be caused due to a change to the UE's subscriptioninformation), the UE 150 may delete previous configuration informationstored locally at the UE (yes at 208, 210). The deleted configurationinformation may include network slicing configuration information, suchas the configured NSSAI for the PLMN, its mapping to the S-NSSAIs in theconfigured NSSAI for the HLMN, the allowed NSSAI and its mapping to theS-NSSAIs in the configured NSSAI for the HPLMN, any rejected S-NSSAIs inthe PLMN and/or the like. Moreover, the deleted configurationinformation may be for some, if not all, other VPLMNs. For example, theUE 150 may delete the previously stored network slicing configurationinformation stored for all VPLMNs. More specifically, the UE 150 maydelete the slicing information for all other PLMNs while retaining any“current” configuration received at 205 for the currently serving VPLMN.

During registration with the network, the UE 150 may register in anotherVPLMN, in which case the UE may not send a request for NSSAI(s) but, at220, instead receive, from the network, configuration informationincluding the network slicing configuration information for the VPLMN,when the indication represents the HPLMN configuration change. Thisconfiguration information may include slice identifiers, such as anS-NSSAI, for use at a VPLMN, and their mapping to the values used in theHPLMN.

In some example embodiments, the UE 150 may wait in the serving PLMN foran updated policy, such as an URSP (UE Route and access Selectionpolicy) from the network before the UE 150 performs a new registrationprocedure, at 220, as the URSP may also change, when the UE subscriptionto the S-NSSAIs has changed.

When the indication represents a local, VPLMN configuration change, theUE 150 may update the stored configuration information including networkslicing information for the serving VPLMN without affecting (e.g.,deleting, updating, etc.) the configuration for the other PLMNs (no at208, 230). In some example embodiments, the UE may determine the UEconfiguration change is a local one based on not receiving anindication.

FIG. 3 depicts an example of a process 300, in accordance with someexample embodiments. The description of FIG. 2 refers to FIG. 1 as well.

At 310, a network node, such as a base station 152, may receive from theAMF 154 configuration information and/or an indication regarding whetherthe configuration information represents a change, such as an update ormodification, that is local to a VPLMN or a change associated with theHPLMN, in accordance with some example embodiments. At 320, the networknode may provide to the UE 150 the configuration information and/or theindication regarding whether the configuration information representsthe change, such as an update or a modification, that is local to aVPLMN or a change associated with the HPLMN.

In some example embodiments, when an AMF, such as AMF 154, updates theUE 150, the AMF may indicate to the UE (via the base station 152)whether the update is due to changes in the subscribed S-NSSAIs. The AMFmay detect this update or change because the AMF receives updated datafrom the UDM 178 or because the AMF receives an indication from the UDMthat the UE's network slicing subscription has changed.

If the UE 150 is informed that network slicing subscription informationhas changed then the UE 150 may, as noted, locally delete the networkslicing information the UE 150 has for all other PLMNs (i.e., so when itregisters in other PLMNs it sends no requested NSSAI and the servingPLMN may updates the UE configuration for the serving PLMN). It alsoupdates the current PLMN information with any received values. And, ifthe URSP is needed, it awaits for an updated URSP (UE Route and accessSelection policy) before performing a new Registration procedure.

In some example embodiments, when the subscribed S-NSSAIs change andwhen the UE 150 is not reachable at the time of change, a Universal DataRepository (UDR) flag may be set in the HPLMN to make sure the AMF(e.g., AMF 154) is informed that the subscription data includes anupdated set of S-NSSAIs, when the UE 150 registers with an AMF in a PLMNwhen it is reachable. Since the AMF updates successfully the UE, the UEmay be requested to register with an indication to the AMF to update theUDM 178 to reset this flag.

To illustrate further, the S-NSSAIs (which may be in the configuredNSSAI for an HPLMN) may, at the time when they are provided to the UE150, match the subscribed S-NSSAIs for the UE 150. When the subscribedS-NSSAI(s) are updated (e.g., by removing an old S-NSSAI and/or adding anew S-NSSAI) for the serving PLMN that the UE 150 is registered in, theAMF 154 may update (via the base station 152 labeled “(R)AN”) the UE 150with the configured NSSAI of the serving VPLMN, allowed NSSAI, and/or anassociated mapping with configured NSSAI for the HPLMN. But as notedabove, only the configured NSSAI for the current serving VPLMN will beupdated to match the new subscription information. As such, if the UE150 visits another VPLMN different from the HPLMN and it has aconfigured NSSAI stored for this VPLMN, this information will be out ofdate. The UE 150 may store the configured NSSAI for several VPLMNs inaddition to the current, serving VPLMN, so that the UE 150 may not needto be configured with the configured NSSAI when returning to theseVPLMNs.

The configured NSSAI for the serving PLMN includes the S-NSSAI values,which can be used in the serving PLMN and may be associated with mappingof each S-NSSAI of the configured NSSAI to one or more correspondingS-NSSAI values in the configured NSSAI for the HPLMN. When providing arequested NSSAI to the network upon registration, the UE 150 in a givenPLMN may include and use S-NSSAIs applying to this PLMN (which mayinclude be associated with mapping of each S-NSSAI of the requestedNSSAI to the S-NSSAIs of the configured NSSAI for the HPLMN that is apart of the configured and/or allowed NSSAIs applicable for this PLMN).Upon successful completion of a UE's registration procedure over a radioaccess type, the UE 150 may obtain an allowed NSSAI for this accesstype, which includes one or more S-NSSAIs from the AMF (which mayinclude associated with mapping of allowed NSSAI to configured NSSAI forthe HPLMN). These S-NSSAIs are valid for the current registration areaand access type provided by the AMF the UE has registered with and maybe used by the UE (up to a given number of simultaneous network slicesor PDU Sessions).

When the UE 150 is provisioned with a configured NSSAI for a PLMN and/orthe associated mapping of this configured NSSAI to the configured NSSAIfor the HPLMN, the configured NSSAI (and/or if present the associatedmapping) may both be stored in the UE 150 until a new configured NSSAIfor this PLMN (and/or the associated mapping) are provisioned in the UE150.

When provisioned with a new configured NSSAI for a PLMN (and/or the newassociated mapping of this configured NSSAI to the configured NSSAI forthe HPLMN), the UE 150 may, as noted, replace any stored (old)configured NSSAI for this PLMN with the new configured NSSAI for thisPLMN; and the UE 150 may delete any stored associated mapping of thisold configured NSSAI for this PLMN to the configured NSSAI for the HPLMNand, if present, store the associated mapping of this new configuredNSSAI to the configured NSSAI for the HPLMN; and the UE 150 may deleteany stored allowed NSSAI and associated mapping as well as rejectedS-NSSAI for this PLMN.

The UE 150 may keep storing the received configured NSSAI for a PLMN andassociated mapping to the configured NSSAI for the HPLMN even whenregistering in another PLMN. However, the number of configured NSSAI andassociated mapping to be kept stored in the UE 150 for PLMNs other thanthe HPLMN may be up to UE implementation.

If the VPLMN performs the configuration update of a UE 150 registered inthe VPLMN (e.g. due to a change in the Subscribed S-NSSAI(s)), this mayresult in updates to the configured NSSAI for the serving PLMN and/or tothe associated mapping of the configured NSSAI for the serving PLMN tothe configured NSSAI for the HPLMN. Updates to the allowed NSSAI and/orto the associated mapping of the allowed NSSAI to the configured NSSAIfor the HPLMN may be implemented if the configuration update affectsS-NSSAI(s) in the current allowed NSSAI.

The UE 150 may replace only the configured NSSAI for the current PLMNwhen the configured NSSAI changes. This is the correct behavior when thechange is due to a VPLMN decision for the VPLMN. However, when thechange is due to subscription changes, the STORED configured NSSAIs andmappings to the S-NSSAI values in the configured NSSAI for the HPLMN forOther PLMNs also becomes invalid and stale. However, the AMF in otherPLMNs may not be receiving the updated configuration (nor are the otherPLMNs aware of this change), so these PLMNs will not trigger aconfigured NSSAI change due to subscription change. This means the UE150 will not be properly configured when returning to these PLMNs.

When no requested NSSAI was included or when an S-NSSAI was rejected inthe PLMN, the AMF may update the UE slice configuration information forthe PLMN.

The UE 150 may include no requested NSSAI in a VPLMN registrationrequest when it has no configuration for the VPLMN. The VPLMN, ifapplicable, may then configure the UE 150 with the configured NSSAI forthe PLMN. When a PLMN updates the configured NSSAI for a UE 150, thePLMN may, as noted, explicitly indicate to the UE 150 whether the changeis dues to a local configuration change, or whether it is due to changein HPLMN configuration. If the change is due to HPLMN configurationchange then (1) the UE 150 may locally delete the network slicingconfiguration information it has for all other PLMNs and may wait for anupdated URSP before performing a new Registration procedure, as the URSPalso changes when the US subscription to S-NSSAIs has changed. And ifthe change is due only to a local, serving PLMN reason, the UE 150 mayupdates the information for the serving PLMN with no consequences forthe configuration for other PLMNs.

As noted, the UE 150 may be configured by the HPLMN with network sliceconfiguration information. For example, the HPLMN may push to the UDMthe configuration information, which may be provided to the UE 150 viathe AMF and base station. The network slice configuration informationmay include one or more configured NSSAI(s). A configured NSSAI mayapply either to one PLMN or to all PLMNs that do not have a specificconfigured NSSAI (e.g. this could be possible for NSSAIs containing onlyS-NSSAIs with standard values, see, e.g., 3GPP TS 23.501, clause5.15.2.1). There is at most one configured NSSAI per PLMN. Theconfigured NSSAI of a PLMN may include S-NSSAIs that have standardvalues or PLMN-specific values. The configured NSSAI for the servingPLMN may include the S-NSSAI values which can be used in the servingPLMN and may be associated with mapping of each S-NSSAI of theconfigured NSSAI to one or more corresponding S-NSSAI values in theconfigured NSSAI for the HPLMN.

The S-NSSAIs in the configured NSSAI for the HPLMN, at the time whenthey are provided to the UE 150, may, as noted, match the subscribedS-NSSAIs for the UE 150. When the subscribed S-NSSAI(s) are updated(e.g., removing an old and/or adding a new) and it is applicable to theServing PLMN the UE 150 may be registered in, the AMF may update the UE150 with the configured NSSAI of the serving PLMN and/or allowed NSSAIand/or the associated mapping with configured NSSAI for the HPLMN.

When providing a requested NSSAI to the network upon registration, theUE 150 in a given PLMN may only include and use the S-NSSAIs applicableto this PLMN (and possibly associated with mapping of each S-NSSAI ofthe requested NSSAI to the S-NSSAIs of the configured NSSAI for theHPLMN that is part of the configured and/or allowed NSSAIs applicablefor this PLMN). Upon successful completion of a UE's registrationprocedure over an access type, the UE 150 may obtain an allowed NSSAIfor this access type, which includes one or more S-NSSAIs, from the AMF,possibly associated with mapping of allowed NSSAI to configured NSSAIfor the HPLMN. These S-NSSAIs may be valid for the current registrationarea and access type provided by the AMF the UE has registered with, andmay be used simultaneously by the UE 150 (up to the maximum number ofsimultaneous network slices or PDU sessions). The UE 150 might alsoobtain one or more rejected S-NSSAIs with cause and validity ofrejection from the AMF. An S-NSSAI may be rejected for the entire PLMNor for the current registration area.

While the UE 150 remains RM-REGISTERED in the PLMN and regardless of theaccess type, the UE 150 may not re-attempt to register to an S-NSSAIrejected for the entire PLMN until this rejected S-NSSAI is deleted.While the UE 150 remains RM-REGISTERED in the PLMN, the UE 150 may notre-attempt to register to an S-NSSAI rejected in the currentRegistration Area until it moves out of the current Registration Area.

The UE 150 may store the (S-)NSSAIs as follows. When the UE 150 isprovisioned with a configured NSSAI for a PLMN and/or the associatedmapping of this configured NSSAI to the configured NSSAI for the HPLMN,the configured NSSAI (and/or if present, the associated mapping) may bestored in the UE 150 until a new configured NSSAI for this PLMN and/orthe associated mapping are provisioned in the UE (or when the HPLMNconfiguration changes. When provisioned with a new configured NSSAI fora PLMN and/or the new associated mapping of this configured NSSAI to theconfigured NSSAI for the HPLMN, or when requested to remove theconfiguration for PLMN due to HPLMN configuration change, the UE 150 mayreplace any stored (e.g., old) configured NSSAI for this PLMN with thenew configured NSSAI for this PLMN (if applicable); and the UE 150 maydelete any stored associated mapping of this old configured NSSAI forthis PLMN to the configured NSSAI for the HPLMN and, if present andapplicable, store the associated mapping of this new configured NSSAI tothe configured NSSAI for the HPLMN; and the UE 150 may delete any storedallowed NSSAI and associated mapping as well as rejected S-NSSAI forthis PLMN;

If received, the allowed NSSAI for a PLMN and access type (and anyassociated mapping of this allowed NSSAI to the configured NSSAI for theHPLMN) may be stored in the UE 150. The UE 150 may store this allowedNSSAI and any associated mapping of the allowed NSSAI to the configuredNSSAI for the HPLMN (which may also be persisted when the UE is turnedoff).

The UE 150 may persistently store the allowed NSSAI and any associatedmapping of the allowed NSSAI to the configured NSSAI for the HPLMN.

If received, an S-NSSAI rejected for the entire PLMN may be stored inthe UE 150 while RM-REGISTERED in this PLMN regardless of the accesstype or until it is deleted.

If received, an S-NSSAI rejected for the current Registration Area maybe stored in the UE 150 while RM-REGISTERED until the UE moves out ofthe current Registration Area or until it is deleted.

One or more S-NSSAIs in an allowed NSSAI provided to the UE 150 may havevalues, which are not part of the UE's slice configuration informationfor the serving PLMN. In this case, the allowed NSSAI is associated withmapping information regarding how each S-NSSAI of the allowed NSSAIcorresponds to the S-NSSAI(s) of the configured NSSAI for the HPLMN.This mapping information may be sufficient to allow the UE 150 toassociate for a given application the S-NSSAI as per network sliceselection policy (NSSP) of the URSP rules (see, e.g., rules defined inTS 23.503) with the corresponding S-NSSAI from the allowed NSSAI.

At any time, the AMF 154 may provide the UE 150 with a new configuredNSSAI for the serving PLMN associated with mapping of the configuredNSSAI to the configured NSSAI for the HPLMN. The configured NSSAI forthe serving PLMN and the mapping information may be determined in theAMF 154 (if based on configuration, the AMF 154 is allowed to determinethe Network Slice configuration for the whole PLMN) or determined by theNSSF. The AMF 154 may provide the new configured NSSAI as part of a UEconfiguration update procedure.

If the HPLMN performs the configuration update of a UE 150 registered inthe HPLMN (e.g. due to a change in the subscribed S-NSSAI(s)), this mayresult in updates to the configured NSSAI for the HPLMN. Updates to theallowed NSSAI and/or, if present, to the associated mapping of theallowed NSSAI to the configured NSSAI for the HPLMN may also possible ifthe configuration update affects S-NSSAI(s) in the current allowedNSSAI.

If the VPLMN performs the configuration update of a UE 150 registered inthe VPLMN (e.g. due to a change in the Subscribed S-NSSAI(s)), this mayresult in updates to the configured NSSAI for the serving PLMN and/or tothe associated mapping of the configured NSSAI for the serving PLMN tothe configured NSSAI for the HPLMN. Updates to the allowed NSSAI and/orto the associated mapping of the allowed NSSAI to the configured NSSAIfor the HPLMN may also be implemented if the configuration updateaffects S-NSSAI(s) in the current allowed NSSAI.

A UE 150 for which the configured NSSAI for the serving PLMN has beenupdated and has deleted the stored allowed NSSAI may, as noted, initiatea registration procedure to receive a new valid allowed NSSAI.

FIG. 4 depicts a block diagram of a network node 400, in accordance withsome example embodiments. The network node 400 may be configured toprovide one or more network side operations as described with respect toFIG. 3 , for example. Moreover, a mobile wireless network may have aplurality of the network nodes 400 as well. For example, the networknode may be incorporated into one or more of the devices 152-180.

The network node 400 may include a network interface 402, a processor420, and a memory 404, in accordance with some example embodiments. Thenetwork interface 402 may include wired and/or wireless transceivers toenable access other nodes including base stations, devices 152-180, theInternet, and/or other nodes. The memory 404 may comprise volatileand/or non-volatile memory including program code, which when executedby at least one processor 420 provides, among other things, theprocesses disclosed herein including process 200, 300, 400, and/or thelike.

FIG. 5 illustrates a block diagram of an apparatus 10, in accordancewith some example embodiments.

The apparatus 10 may represent a user equipment, such as the userequipment 150. The apparatus 10, or portions therein, may be implementedin other network nodes including base stations/WLAN access points aswell as the other network nodes (e.g., devices 152-184).

The apparatus 10 may include at least one antenna 12 in communicationwith a transmitter 14 and a receiver 16. Alternatively transmit andreceive antennas may be separate. The apparatus 10 may also include aprocessor 20 configured to provide signals to and receive signals fromthe transmitter and receiver, respectively, and to control thefunctioning of the apparatus. Processor 20 may be configured to controlthe functioning of the transmitter and receiver by effecting controlsignalling via electrical leads to the transmitter and receiver.Likewise, processor 20 may be configured to control other elements ofapparatus 10 by effecting control signalling via electrical leadsconnecting processor 20 to the other elements, such as a display or amemory. The processor 20 may, for example, be embodied in a variety ofways including circuitry, at least one processing core, one or moremicroprocessors with accompanying digital signal processor(s), one ormore processor(s) without an accompanying digital signal processor, oneor more coprocessors, one or more multi-core processors, one or morecontrollers, processing circuitry, one or more computers, various otherprocessing elements including integrated circuits (for example, anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), and/or the like), or some combination thereof.Accordingly, although illustrated in FIG. 5 as a single processor, insome example embodiments the processor 20 may comprise a plurality ofprocessors or processing cores.

The apparatus 10 may be capable of operating with one or more airinterface standards, communication protocols, modulation types, accesstypes, and/or the like. Signals sent and received by the processor 20may include signalling information in accordance with an air interfacestandard of an applicable cellular system, and/or any number ofdifferent wireline or wireless networking techniques, comprising but notlimited to Wi-Fi, wireless local access network (WLAN) techniques, suchas Institute of Electrical and Electronics Engineers (IEEE) 802.11,802.16, 802.3, ADSL, DOCSIS, and/or the like. In addition, these signalsmay include speech data, user generated data, user requested data,and/or the like.

For example, the apparatus 10 and/or a cellular modem therein may becapable of operating in accordance with various first generation (1G)communication protocols, second generation (2G or 2.5G) communicationprotocols, third-generation (3G) communication protocols,fourth-generation (4G) communication protocols, fifth-generation (5G)communication protocols, Internet Protocol Multimedia Subsystem (IMS)communication protocols (for example, session initiation protocol (SIP)and/or the like. For example, the apparatus 10 may be capable ofoperating in accordance with 2G wireless communication protocols IS-136,Time Division Multiple Access TDMA, Global System for Mobilecommunications, GSM, IS-95, Code Division Multiple Access, CDMA, and/orthe like. In addition, for example, the apparatus 10 may be capable ofoperating in accordance with 2.5G wireless communication protocolsGeneral Packet Radio Service (GPRS), Enhanced Data GSM Environment(EDGE), and/or the like. Further, for example, the apparatus 10 may becapable of operating in accordance with 3G wireless communicationprotocols, such as Universal Mobile Telecommunications System (UMTS),Code Division Multiple Access 2000 (CDMA2000), Wideband Code DivisionMultiple Access (WCDMA), Time Division-Synchronous Code DivisionMultiple Access (TD-SCDMA), and/or the like. The apparatus 10 may beadditionally capable of operating in accordance with 3.9G wirelesscommunication protocols, such as Long Term Evolution (LTE), EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN), and/or the like.Additionally, for example, the apparatus 10 may be capable of operatingin accordance with 4G wireless communication protocols, such as LTEAdvanced, 5G, and/or the like as well as similar wireless communicationprotocols that may be subsequently developed.

It is understood that the processor 20 may include circuitry forimplementing audio/video and logic functions of apparatus 10. Forexample, the processor 20 may comprise a digital signal processordevice, a microprocessor device, an analog-to-digital converter, adigital-to-analog converter, and/or the like. Control and signalprocessing functions of the apparatus 10 may be allocated between thesedevices according to their respective capabilities. The processor 20 mayadditionally comprise an internal voice coder (VC) 20 a, an internaldata modem (DM) 20 b, and/or the like. Further, the processor 20 mayinclude functionality to operate one or more software programs, whichmay be stored in memory. In general, processor 20 and stored softwareinstructions may be configured to cause apparatus 10 to perform actions.For example, processor 20 may be capable of operating a connectivityprogram, such as a web browser. The connectivity program may allow theapparatus 10 to transmit and receive web content, such as location-basedcontent, according to a protocol, such as wireless application protocol,WAP, hypertext transfer protocol, HTTP, and/or the like.

Apparatus 10 may also comprise a user interface including, for example,an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, auser input interface, and/or the like, which may be operationallycoupled to the processor 20. The display 28 may, as noted above, includea touch sensitive display, where a user may touch and/or gesture to makeselections, enter values, and/or the like. The processor 20 may alsoinclude user interface circuitry configured to control at least somefunctions of one or more elements of the user interface, such as thespeaker 24, the ringer 22, the microphone 26, the display 28, and/or thelike. The processor 20 and/or user interface circuitry comprising theprocessor 20 may be configured to control one or more functions of oneor more elements of the user interface through computer programinstructions, for example, software and/or firmware, stored on a memoryaccessible to the processor 20, for example, volatile memory 40,non-volatile memory 42, and/or the like. The apparatus 10 may include abattery for powering various circuits related to the mobile terminal,for example, a circuit to provide mechanical vibration as a detectableoutput. The user input interface may comprise devices allowing theapparatus 20 to receive data, such as a keypad 30 (which can be avirtual keyboard presented on display 28 or an externally coupledkeyboard) and/or other input devices.

As shown in FIG. 5 , apparatus 10 may also include one or moremechanisms for sharing and/or obtaining data. For example, the apparatus10 may include a short-range radio frequency (RF) transceiver and/orinterrogator 64, so data may be shared with and/or obtained fromelectronic devices in accordance with RF techniques. The apparatus 10may include other short-range transceivers, such as an infrared (IR)transceiver 66, a Bluetooth™ (BT) transceiver 68 operating usingBluetooth™ wireless technology, a wireless universal serial bus (USB)transceiver 70, a Bluetooth™ Low Energy transceiver, a ZigBeetransceiver, an ANT transceiver, a cellular device-to-devicetransceiver, a wireless local area link transceiver, and/or any othershort-range radio technology. Apparatus 10 and, in particular, theshort-range transceiver may be capable of transmitting data to and/orreceiving data from electronic devices within the proximity of theapparatus, such as within 10 meters, for example. The apparatus 10including the Wi-Fi or wireless local area networking modem may also becapable of transmitting and/or receiving data from electronic devicesaccording to various wireless networking techniques, including 6LoWpan,Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques,IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.

The apparatus 10 may comprise memory, such as a subscriber identitymodule (SIM) 38, a removable user identity module (R-UIM), an eUICC, anUICC, and/or the like, which may store information elements related to amobile subscriber. In addition to the SIM, the apparatus 10 may includeother removable and/or fixed memory. The apparatus 10 may includevolatile memory 40 and/or non-volatile memory 42. For example, volatilememory 40 may include Random Access Memory (RAM) including dynamicand/or static RAM, on-chip or off-chip cache memory, and/or the like.Non-volatile memory 42, which may be embedded and/or removable, mayinclude, for example, read-only memory, flash memory, magnetic storagedevices, for example, hard disks, floppy disk drives, magnetic tape,optical disc drives and/or media, non-volatile random access memory(NVRAM), and/or the like. Like volatile memory 40, non-volatile memory42 may include a cache area for temporary storage of data. At least partof the volatile and/or non-volatile memory may be embedded in processor20. The memories may store one or more software programs, instructions,pieces of information, data, and/or the like which may be used by theapparatus for performing operations disclosed herein. Alternatively oradditionally, the apparatus 10 may be configured to cause the operationsdisclosed herein with respect to the base stations/WLAN access pointsand network nodes including the UEs.

The memories may comprise an identifier, such as an international mobileequipment identification (IMEI) code, capable of uniquely identifyingapparatus 10. The memories may comprise an identifier, such as aninternational mobile equipment identification (IMEI) code, capable ofuniquely identifying apparatus 10. In the example embodiment, theprocessor 20 may be configured using computer code stored at memory 40and/or 42 to the provide operations disclosed herein with respect to thebase stations/WLAN access points and network nodes including the UEs(see, e.g., process 200 and/or 300).

Some of the embodiments disclosed herein may be implemented in software,hardware, application logic, or a combination of software, hardware, andapplication logic. The software, application logic, and/or hardware mayreside on memory 40, the control apparatus 20, or electronic components,for example. In some example embodiment, the application logic, softwareor an instruction set is maintained on any one of various conventionalcomputer-readable media. In the context of this document, a“computer-readable medium” may be any non-transitory media that cancontain, store, communicate, propagate or transport the instructions foruse by or in connection with an instruction execution system, apparatus,or device, such as a computer or data processor circuitry, with examplesdepicted at FIG. 5 , computer-readable medium may comprise anon-transitory computer-readable storage medium that may be any mediathat can contain or store the instructions for use by or in connectionwith an instruction execution system, apparatus, or device, such as acomputer.

Without in any way limiting the scope, interpretation, or application ofthe claims appearing below, a technical effect of one or more of theexample embodiments disclosed herein may be improved UE configuration.

The subject matter described herein may be embodied in systems,apparatus, methods, and/or articles depending on the desiredconfiguration. For example, the base stations and user equipment (or oneor more components therein) and/or the processes described herein can beimplemented using one or more of the following: a processor executingprogram code, an application-specific integrated circuit (ASIC), adigital signal processor (DSP), an embedded processor, a fieldprogrammable gate array (FPGA), and/or combinations thereof. Thesevarious implementations may include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device. Thesecomputer programs (also known as programs, software, softwareapplications, applications, components, program code, or code) includemachine instructions for a programmable processor, and may beimplemented in a high-level procedural and/or object-orientedprogramming language, and/or in assembly/machine language. As usedherein, the term “computer-readable medium” refers to any computerprogram product, machine-readable medium, computer-readable storagemedium, apparatus and/or device (for example, magnetic discs, opticaldisks, memory, Programmable Logic Devices (PLDs)) used to providemachine instructions and/or data to a programmable processor, includinga machine-readable medium that receives machine instructions. Similarly,systems are also described herein that may include a processor and amemory coupled to the processor. The memory may include one or moreprograms that cause the processor to perform one or more of theoperations described herein.

Although a few variations have been described in detail above, othermodifications or additions are possible. In particular, further featuresand/or variations may be provided in addition to those set forth herein.Moreover, the implementations described above may be directed to variouscombinations and sub-combinations of the disclosed features and/orcombinations and sub-combinations of several further features disclosedabove. Other embodiments may be within the scope of the followingclaims.

If desired, the different functions discussed herein may be performed ina different order and/or concurrently with each other. Furthermore, ifdesired, one or more of the above-described functions may be optional ormay be combined. Although various aspects of some of the embodiments areset out in the independent claims, other aspects of some of theembodiments comprise other combinations of features from the describedembodiments and/or the dependent claims with the features of theindependent claims, and not solely the combinations explicitly set outin the claims. It is also noted herein that while the above describesexample embodiments, these descriptions should not be viewed in alimiting sense. Rather, there are several variations and modificationsthat may be made without departing from the scope of some of theembodiments as defined in the appended claims. Other embodiments may bewithin the scope of the following claims. The term “based on” includes“based on at least.” The use of the phase “such as” means “such as forexample” unless otherwise indicated.

1. A method performed by a user equipment, the method comprising:registering with a first visited public land mobile network (VPLMN);while registered with the first VPLMN, receiving an indication thatnetwork slicing subscription information of the user equipment haschanged in a home public land mobile network (HPLMN) of the userequipment; in response to receiving said indication, deleting aconfigured network slice selection assistance information (NSSAI) storedby the user equipment for a second VPLMN, different than the firstVPLMN; and following deleting of the configured NSSAI for the secondVPLMN and upon registering with the second VPLMN, receiving anotherconfigured NSSAI for said second VPLMN without sending a requested NSSAIfor the second VPLMN.
 2. The method of claim 1, wherein receiving saidindication that network slicing subscription information of the userequipment has changed in the HPLMN of the user equipment causes the userequipment to operate as if the user equipment needs initial networkslicing configuration information for said second VPLMN.
 3. The methodof claim 1, wherein receiving another configured NSSAI for said secondVPLMN is caused by the user equipment operating as if the user equipmentis visiting the second VPLMN for a first time with respect to needingnetwork slicing configuration information.
 4. The method of claim 1,wherein deleting said configured NSSAI comprises deleting a mapping ofthe configured NSSAI for the second VPLMN to a configured NSSAI for saidHPLMN and deleting the configured NSSAI for said HPLMN.
 5. The method ofclaim 1, further comprising: receiving a configured NSSAI for the firstVPLMN in addition to the indication; and updating network slicingconfiguration information for the first VPLMN based upon the configuredNSSAI received in addition to the indication.
 6. The method of claim 1,wherein deleting said configured NSSAI for said second VPLMN comprisesdeleting the configured NSSAI that applies to said second VPLMN, amapping of the configured NSSAI that applies to said first VPLMN tosingle NSSAIs (S-NSSAIs) in a configured NSSAI for the HPLMN, an allowedNSSAI in the first VPLMN and a mapping of the allowed NSSAI to theS-NSSAIs in the configured NSSAI for the HPLMN or any rejected S-NSSAIsin the first VPLMN.
 7. The method of claim 1, further comprising:deleting, in response to receiving said indication, configured NSSAIsfor all other public land mobile networks that were previously stored atthe user equipment.
 8. A user equipment comprising: at least oneprocessor; and at least one memory storing instructions that, whenexecuted by the at least one processor, cause the user equipment toperform at least: registering with a first visited public land mobilenetwork (VPLMN); while registered with the first VPLMN, receiving anindication that network slicing subscription information of the userequipment has changed in a home public land mobile network (HPLMN) ofthe user equipment; in response to receiving said indication, deleting aconfigured network slice selection assistance information (NSSAI) storedby the user equipment for a second VPLMN, different than the firstVPLMN; and following deleting of the configured NSSAI for the secondVPLMN and upon registering with the second VPLMN, receiving anotherconfigured NSSAI for said second VPLMN without sending a requested NSSAIfor the second VPLMN.
 9. The user equipment of claim 8, whereinreceiving indication that network slicing subscription information ofthe user equipment has changed in the HPLMN of the user equipment causesthe user equipment to operate as if the user equipment needs initialnetwork slicing configuration information for said second VPLMN.
 10. Theuser equipment of claim 8, wherein receiving another configured NSSAIfor said second VPLMN is caused by the user equipment operating as ifthe user equipment is visiting the second VPLMN for a first time withrespect to needing network slicing configuration information.
 11. Theuser equipment of claim 8, wherein deleting said configured NSSAIcomprises deleting a mapping of the configured NSSAI for the secondVPLMN to a configured NSSAI for said HPLMN and deleting the configuredNSSAI for said HPLMN.
 12. The user equipment of claim 8, wherein theinstructions, when executed by the at least one processor, furthercauses the user equipment to perform: receiving a configured NSSAI forthe first VPLMN in addition to the indication; and updating networkslicing configuration information for the first VPLMN based upon theconfigured NSSAI received in addition to the indication.
 13. The userequipment of claim 8, wherein deleting said configured NSSAI for saidsecond VPLMN comprises deleting the configured NSSAI that applies tosaid second VPLMN, a mapping of the configured NSSAI that applies tosaid first VPLMN to single NSSAIs (S-NSSAIs) in a configured NSSAI forthe HPLMN, an allowed NSSAI in the first VPLMN and a mapping of theallowed NSSAI to the S-NSSAIs in the configured NSSAI for the HPLMN orany rejected S-NSSAIs in the first VPLMN.
 14. The user equipment ofclaim 8, wherein the instructions, when executed by the at least oneprocessor, further causes the user equipment to perform: deleting, inresponse to receiving said indication, configured NSSAIs for all otherpublic land mobile networks that were previously stored at the userequipment. 15-21. (canceled)
 22. A method performed by a user equipment,the method comprising: registering with a first visited public landmobile network (VPLMN); while registered with the first VPLMN, receivingan indication that network slicing subscription information of the userequipment has changed in a home public land mobile network (HPLMN) ofthe user equipment; in response to receiving said indication, deleting aconfigured network slice selection assistance information (NSSAI) storedby the user equipment for a second VPLMN, the second VPLMN beingdifferent than the first VPLMN; and in response to deleting of theconfigured NSSAI for the second VPLMN and upon subsequently roaming tothe second VPLMN, registering with the second VPLMN in a mannerconsistent with how the user equipment would operate when visiting thesecond VPLMN for a first time with respect to requesting initial networkslicing configuration information.
 23. The method of claim 22, whereinsaid registering with the second VPLMN in a manner consistent with howthe user equipment would operate when visiting the second VPLMN for afirst time with respect to requesting initial network slicingconfiguration information comprises: generating a message comprising aregistration request for registration of the user equipment with thesecond VPLMN; refraining from adding a requested NSSAI for the secondVPLMN to the message; and sending the registration request message tothe second VPLMN.
 24. The method of claim 22, wherein receiving theindication that the network slicing subscription information of the userequipment has changed in a home public land mobile network (HPLMN) ofthe user equipment comprises causing the user equipment to operate as ifthe user equipment needs initial network slicing configurationinformation for said second VPLMN.
 25. The method of claim 22, whereindeleting said configured NSSAI comprises deleting a mapping of theconfigured NSSAI for the second VPLMN to a configured NSSAI for saidHPLMN and deleting the configuration NSSAI for said HPLMN.
 26. Themethod of claim 22, further comprising: receiving a configured NSSAI forthe first VPLMN in addition to the indication; and updating networkslicing configuration information for the first VPLMN based upon theconfigured NSSAI received in addition to the indication.
 27. The methodof claim 22, wherein deleting said configured NSSAI for said secondVPLMN comprises deleting the configured NSSAI that applies to saidsecond VPLMN, a mapping of the configured NSSAI that applies to saidfirst VPLMN to single NSSAIs (S-NSSAIs) in a configured NSSAI for theHPLMN, an allowed NSSAI in the first VPLMN and a mapping of the allowedNSSAI to the S-NSSAIs in the configured NSSAI for the HPLMN or anyrejected S-NSSAIs in the first VPLMN.
 28. The method of claim 22,further comprising: deleting, in response to receiving said indication,configured NSSAIs for all other public land mobile networks that werepreviously stored at the user equipment.
 29. A user equipmentcomprising: at least one processor; and at least one memory storinginstructions that, when executed by the at least one processor, causethe user equipment to perform at least: registering with a first visitedpublic land mobile network (VPLMN); while registered with the firstVPLMN, receiving an indication that network slicing subscriptioninformation of the user equipment has changed in a home public landmobile network (HPLMN) of the user equipment; in response to receivingsaid indication, deleting a configured network slice selectionassistance information (NSSAI) stored by the user equipment for a secondVPLMN, the second VPLMN being different than the first VPLMN; and inresponse to deleting of the configured NSSAI for the second VPLMN andupon subsequently roaming to the second VPLMN, registering with thesecond VPLMN in a manner consistent with how the user equipment wouldoperate when visiting the second VPLMN for a first time with respect torequesting initial network slicing configuration information.
 30. Theuser equipment of claim 29, wherein the instructions, when executed bythe at least one processor, further cause the user equipment to registerwith the second VPLMN in a manner consistent with how the user equipmentwould operate when visiting the second VPLMN for a first time withrespect to requesting initial network slicing configuration informationby: generating a message comprising a registration request forregistration of the user equipment with the second VPLMN; refrainingfrom adding a requested NSSAI for the second VPLMN to the message; andsending the registration request message to the second VPLMN.
 31. Theuser equipment of claim 29, wherein the instructions, when executed bythe at least one processor, based upon receiving the indication that thenetwork slicing subscription information of the user equipment haschanged in a home public land mobile network (HPLMN) of the userequipment, causes the user equipment to operate as if the user equipmentneeds initial network slicing configuration information for said secondVPLMN.
 32. The user equipment of claim 29, wherein deleting saidconfigured NSSAI comprises deleting a mapping of the configured NSSAIfor the second VPLMN to a configured NSSAI for said HPLMN and deletingthe configuration NSSAI for said HPLMN.
 33. The user equipment of claim29, wherein the instructions, when executed by the at least oneprocessor, further cause the user equipment to perform: receiving aconfigured NSSAI for the first VPLMN in addition to the indication; andupdating network slicing configuration information for the first VPLMNbased upon the configured NSSAI received in addition to the indication.34. The user equipment of claim 29, wherein deleting said configuredNSSAI for said second VPLMN comprises deleting the configured NSSAI thatapplies to said second VPLMN, a mapping of the configured NSSAI thatapplies to said first VPLMN to single NSSAIs (S-NSSAIs) in a configuredNSSAI for the HPLMN, an allowed NSSAI in the first VPLMN and a mappingof the allowed NSSAI to the S-NSSAIs in the configured NSSAI for theHPLMN or any rejected S-NSSAIs in the first VPLMN.
 35. The userequipment of claim 29, wherein the instructions, when executed by the atleast one processor, further cause the user equipment to perform:deleting, in response to receiving said indication, configured NSSAIsfor all other public land mobile networks that were previously stored atthe user equipment. 36-42. (canceled)